Document global placement, GPU preference lists, and global storage#298
Merged
Conversation
Rewrite Multi-Region Deployment around intent-based placement: region = "global" (recommended) or pin a region, geography placement marked coming soon, routing behavior (warm capacity first, soft latency preference, no session affinity), app-wide scaling semantics, and the region list and GPU availability table rebuilt from deploy validation (4 self-serve regions, 10 on request). Document shipped-but-undocumented config: - compute accepts a preference-ordered list of up to 5 types (one hardware family; cerebrium run uses the first entry) - provider and region are optional; defaults are platform-selected Storage, verified against latest CLI/backend/infra tips and live CLI: - Global storage: /global-persistent-storage mount, --region global file commands, per-region read caches - Soften regional isolation claim to "not guaranteed available in other regions" (regional volumes are not all physically isolated) - Fix rm directory syntax (trailing slash required), resize endpoint (PATCH /v2, volume id default-<region>), drop stale 50GB default Secrets are documented as available in every region an app runs in. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…ive API Self-serve regions (us-east-1, us-central1, eu-north-1, eu-north1) all confirmed present in the production GPU availability matrix. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The region list already names eu-north-1 (Stockholm) and eu-north1 (Finland) as separate regions. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
milo157
reviewed
Jul 17, 2026
| memory = 8.0 | ||
| ``` | ||
|
|
||
| Pinning guarantees placement but limits the app to that region's capacity, which increases the likelihood of request queuing when the region is busy. |
Contributor
There was a problem hiding this comment.
"guarantees placement in that region"
- Pinning wording: guarantees placement in that region - Routing: requests enter through the closest region, then route to warm capacity - Storage wording extends to multi-region placement: one independent regional volume per region an app runs in - Replace storage pricing figures with a pricing page link - Note the global volume size (1TB) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
When omitted, the platform chooses placement automatically based on the app's hardware requirements. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
milo157
approved these changes
Jul 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Second PR of the intent-based placement docs work (follows #296).
Multi-Region Deployment rewrite (
deployments/multi-region-deployment.mdx, same path and nav slot):region = "global"as the recommended default: platform places the app in any region with capacity matching its hardware requirements; new regions become eligible without a redeployeu-north-1vseu-north1disambiguation;provider = "nebius"requirement for non-AWS pins. No Crusoe regions listed./global-persistent-storagefor global appsShipped but undocumented config now covered:
computepreference lists (up to 5 types, one hardware family,cerebrium runuses first entry) inusing-gpus+ TOML referenceprovider/regionoptional with platform-selected defaults; Complete Example usesregion = "global"Storage fixes (verified against latest CLI v2.5.3 / backend / infra tips, plus live CLI tests):
managing-files:--region globalfile commands work end to end, per-region read caches, no dashboard listing/resize for the global volumermdirectory syntax requires a trailing slash; resize endpoint corrected to the verifiedPATCH /v2route withdefault-<region>volume id and 50GB-1TB bounds; stale 50GB default removedfaster-cold-starts: per-region cache behavior and global-volume guidance for multi-region appsAlso: secrets documented as available in every region an app runs in; introduction reframed to "deploy once and run across multiple regions".
Open items (flagged during review, need product/eng confirmation)
provider = "crusoe", even though docs no longer mention it; align deploy validation if it should be retiredExcludedRegionsdoes not gate us-west-2/eu-west-2, which docs list as on-request🤖 Generated with Claude Code